Tab: Log

You can view the PLC log on this tab of the generic device editor. It lists the events that were recorded on the target system. This concerns the following:

Events during the startup and shutdown of the system (components loaded, with version)
Application download and loading of the boot application
Custom entries
Log entries from I/O drivers
Log entries from data sources

Tip

The Log tab also opens when you click Open Log Page. You can configure this as a menu command in the Customize dialog.

Table 44. Menu bar

	Refreshes the list of log events for all runtime system component
Components	Filters the display of log events by the runtime system components selected in the list box Example: `CmpApp` displays all events which occur in these components, for example "`Application [ <name> ] loaded via [OnlineChange]`". <all components>: Displays the reported events of all components
	Loads the next page with newer log messages
	Loads the previous page with older log messages
	Loads the page with the newest log entries and enables automatic scrolling
	: Indicates that there are new log messages which have not been displayed yet Tip This is also displayed on the status bar as Auto-Scroll: ON.
	Loads the page with oldest log messages
	Filters events with the severity Warning and notifies about how many Blue-outlined button: Warnings are displayed.
	Filters events with the severity Error and notifies about how many Blue-outlined button: Errors are displayed.
	Filters events with the severity Exception and notifies about how many Blue-outlined button: Exceptions are displayed.
	Filters events with the severity Information and notifies about how many Blue-outlined button: Information is displayed.
	Filters events with the severity Debug and notifies about how many Blue-outlined button: Debug messages are displayed.
Search in messages	Input field for search text When you enter one or more characters in the search field, the logger messages will highlight the hits in yellow.
	Jumps to the next hit
	Jumps to the previous hit
Logger	Enables a logger for displaying its recorded events By default, the `<default logger>` defined by the system is set. For example, that is the logger `PlcLog` for a CODESYS Control Win runtime system. `.Audit.log`: This logger shows all user interactions with the PLC. The user name is also logged. These are actions such as download, start, stop or set breakpoints. Failed attempts are also logged if a user is not allowed to perform certain actions.
UTC time	: Converts the times displayed below Timestamp to the local time of the development system The conversion is based on the time zone of the operating system where the CODESYS is running. (default setting) : Displays the original timestamp of the runtime system If you change the option, then the displayed timestamp is converted automatically.
	Exports the list contents to an xml file You can select the file name and location.
	Imports an XML file with log messages stored in the file system A separate window opens to display the log messages.

Display window with log file	Tabular display of the log messages Ten thousand log messages are displayed per page.
Severity	: Warning : Error : Exception : Information : Debug message
Time stamp	Date and time of the development system or of the runtime system) Example: `1/12/2007 9:48`
Description	Description of the event Example: `PLC started`
Component	Runtime component where the reported event occurred

Table 45. Status bar

Auto-Scroll

Displays whether auto-scrolling is enabled (ON) or disabled (OFF)

ON: The log list is refreshed automatically when changes occur.
OFF: When a new log event occurs, it is displayed next to Off. Moreover, the button is decorated with on the menu bar.

Tip

Hint: Click the button to enable Auto-Scroll.

Note

Error checking

For exceptions with the *SOURCEPOSITION* description, the affected function opens in the editor by double-clicking it or by means of the Display Source Code in Editor command in the context menu. The cursor jumps to the line that is causing the error. You can also perform this diagnosis when you have the CODESYS project archive, including the download information files and the exported log file.

When the affected function is protected, then the following message appears: "The source code is not available for <function name>."

Tip

If a VendorException is reported, then a manufacturer-specific exception error has occurred in the CODESYS runtime. Contact the PLC manufacturer for more information.